Skip to content

ENH: Added -j auto for build cmd #314

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
ganesh-k13 wants to merge 2 commits into
base: main
Choose a base branch
from
Open

ENH: Added -j auto for build cmd #314

ganesh-k13 wants to merge 2 commits into from
+31 −3

Conversation

@ganesh-k13
Copy link
Contributor

@ganesh-k13 ganesh-k13 commented Feb 11, 2026

Changes

  • Added a -j auto for spin build

Testing

(np-test) ➜  numpy git:(main) spin build -j auto
Building with 12 parallel jobs
$ /<>/os/np-test/bin/python3 vendored-meson/meson/meson.py compile -j 12 -C build
INFO: autodetecting backend as ninja
...

We can speed up CI jobs for all NumPy workflows post this using -j auto

@stefanv
Copy link
Member

stefanv commented Feb 11, 2026

I think Meson has this built-in, if you set -j 0? But, it also seems to be on by default (I just checked, and NumPy compilation uses all cores).

@ganesh-k13
Copy link
Contributor Author

ganesh-k13 commented Feb 11, 2026

Oh, my laptop was always using a single core, not sure why. Maybe an issue from my end, let me take a look.

@rgommers
Copy link
Contributor

rgommers commented Feb 11, 2026

This shouldn't be needed indeed. By default, ninja will use 2*n_cpu + 2 build processes (e.g., if your machine has 12 physical cores, it'll use max 26 processes). It isn't even possible to change that with an environment variable, only by explicitly passing -j1. So please look at how ninja gets invoked on your machine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@ganesh-k13 @stefanv @rgommers